chore(deps): update eslint to latest #7273
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![mongodb-devtools-bot[bot]](https://avatars.githubusercontent.com/u/124201131?s=60&v=4){kind=small}
mongodb-devtools-bot
bot
added
the
no-title-validation
mongodb-devtools-bot
bot
force-pushed
the
ci/update-eslint
branch
from
378b0ff to
aa48864
Compare
paula-stacho
approved these changes
Sep 4, 2025
mongodb-devtools-bot
bot
force-pushed
the
ci/update-eslint
branch
4 times, most recently
from
2451f4b to
4500250
Compare
mongodb-devtools-bot
bot
force-pushed
the
ci/update-eslint
branch
from
4500250 to
d8b05e1
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is automatically generated and updates the versions of the dependency group eslint to latest version.
If CI is green on this patch you should feel free to merge it at your convenience.
If CI is red and you think that failures are related to the version updates, you should raise an issue, so that it can be manually resolved and we can continue to update the package group to latest.